Please address the comments from this code review:

## Overall Comments
- In `ui/pages/dashboard/[owner]/[repo]/edit/license.vue`, the `<n-select>` was changed from `v-model:value="licenseId"` to `:value="licenseId"` without wiring an `@update:value` handler, so user selections will no longer update `licenseId` or trigger `updateLicenseContent`; reintroduce `v-model:value` or add an explicit `@update:value` to keep the selection reactive.
- The new archival helpers in `bot/compliance-checks/archival/index.js` add quite a bit of logic; consider moving the identifier/DOI parsing and badge generation into a separate module (e.g., `utils/doi.js`) to keep the archival template function focused and easier to maintain.

## Individual Comments

### Comment 1
<location path="bot/index.js" line_range="46-50" />
<code_context>
-      });
-    }
-  });
+  // Register all event handlers
+  registerInstallationHandlers(app, db);
+  registerPushHandler(app, db);
+  registerPullRequestHandlers(app, db);
+  registerIssueHandlers(app, db);
 };
</code_context>
<issue_to_address>
**issue (bug_risk):** The `db` variable passed into handler registration is undefined; use `dbInstance` instead.

`dbInstance` is the only database export from `./db.js`, and `db` is not defined in this scope. The calls to `registerInstallationHandlers`, `registerPushHandler`, `registerPullRequestHandlers`, and `registerIssueHandlers` will fail at runtime. Replace `db` with `dbInstance` so each handler receives the actual Prisma client instance.
</issue_to_address>

### Comment 2
<location path="bot/compliance-checks/archival/index.js" line_range="219" />
<code_context>
-      const lastVersion = existingZenodoDep.github_tag_name;
-      const zenodoId = existingZenodoDep.zenodo_id;
-      const zenodoDoi = existingZenodoDep.last_published_zenodo_doi;
-      const zenodoDOIBadge = `[![DOI](https://img.shields.io/badge/DOI-${zenodoDoi}-blue)](${ZENODO_ENDPOINT}/records/${zenodoId})`;
-      baseTemplate += `${archiveTitle} ✔️\n\n***${lastVersion}***${alreadyReleaseText}\n\n${zenodoDOIBadge}\n\nReady to create your next FAIR release? Click the button below:\n\n${releaseBadgeButton}\n\n`;
-    }
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Use the new DOI badge helper to avoid label-encoding issues for stored Zenodo DOIs.

This branch still interpolates `zenodoDoi` directly into the shields.io URL, so a stored `last_published_zenodo_doi` containing `/`, `(`, `)`, spaces, or other special characters could break the badge.

To align with the new helpers and centralize encoding, update this to:
```js
const zenodoDOIBadge = createZenodoDOIBadge(zenodoDoi, zenodoId);
```

Suggested implementation:

```javascript
      const lastVersion = existingZenodoDep.github_tag_name;
      const zenodoId = existingZenodoDep.zenodo_id;
      const zenodoDoi = existingZenodoDep.last_published_zenodo_doi;
      const zenodoDOIBadge = createZenodoDOIBadge(zenodoDoi, zenodoId);
      baseTemplate += `${archiveTitle} ✔️\n\n***${lastVersion}***${alreadyReleaseText}\n\n${zenodoDOIBadge}\n\nReady to create your next FAIR release? Click the button below:\n\n${releaseBadgeButton}\n\n`;
    }

```

1. Ensure `createZenodoDOIBadge` is imported or available in this module, matching how it is used elsewhere in the codebase, e.g. an import like:
   `const { createZenodoDOIBadge } = require('./path/to/helpers');`
2. If the helper has a different signature (e.g. expects an object `{ doi, zenodoId }`), adjust the call accordingly to match the existing helper definition.
</issue_to_address>